Pre-license development tool

ABSTRACT

Methods, computer-readable media, software, and apparatuses provide a tool for use by drivers and/or coaches throughout the pre-license stage of obtaining a driver&#39;s license. A pre-license program may control a computing device to collect drive data while a driver is driving a vehicle. This drive data may be used to detect a drive event. Then, the computing device may present coaching information associated with the detected drive event. The coaching information may provide a passenger, such as a coach or parent, with real-time advice for instructing the driver how to improve his/her driving skills. Moreover, the drive data collected may be used to prepare reports providing feedback to the drivers and coaches.

FIELD OF ART

Aspects of the disclosure generally relate to computer systems andcomputer software. More particularly, aspects of this disclosure providea tool for generating feedback for drivers seeking their driver'slicense and assisting others to instruct the drivers throughout thepre-license stage.

BACKGROUND

Car accidents are a common cause of injury and damage, and the costsresulting from car accidents can be significant. The frequency of caraccidents is especially high for young and/or novice drivers. There is ademand to reduce the number of accidents among this group of drivers. Inthe United States, many states require mandatory training for newdrivers. This training may include attending classes and/or taking adriving course with a certified instructor. Further, in many states,prior to obtaining a driver's license, users may receive a drivingpermit that allows them to drive as long as another person with a validdriver's license is in the vehicle. Often this other person is asked ordesires to teach the driver to drive. However, this other person mightnot know how to teach the driver or might want advice on how to teachthe driver.

Accordingly, new systems, devices, methodologies, and software aredesired to provide teaching assistance to passengers, such as parents,driving coaches, etc., to aid in teaching novice drivers, such asteenagers, how to drive.

BRIEF SUMMARY

In light of the foregoing background, the following presents asimplified summary of the present disclosure in order to provide a basicunderstanding of some aspects of the invention. This summary is not anextensive overview of the invention. It is not intended to identify keyor critical elements of the invention or to delineate the scope of theinvention. The following summary merely presents some concepts of theinvention in a simplified form as a prelude to the more detaileddescription provided below.

Aspects of the disclosure address one or more of the issues mentionedabove by disclosing methods, computer readable storage media, software,systems, and apparatuses for providing a tool that tracks progression ofdriving skills and experience of a student as he/she learns to drive.The tool further presents coaching advice to coaches (e.g., parents,friends, etc.) in real-time while the student is driving and feedback tostudents for their review after driving.

Aspects of this disclosure provide computer readable media storingcomputer-executable instructions that, when executed, cause a computingdevice (e.g., a parent's smartphone) to collect drive data (e.g.,acceleration, deceleration, g-force, time of day, etc.) while a driveris driving a vehicle, detect a drive event based on the drive data, andpresent coaching information associated with the drive event in responseto detecting the drive event. A drive event may be, for example, a brakeevent or turn event. The computer-executable instructions may furthercause the computing device to determine the coaching information basedon driver information associated with the driver. In some cases, thisdriver information may be retrieved from another computing deviceassociated with the driver (e.g., a smartphone of the driver). Duringthe drive, the computer-executable instructions may further cause thecomputing device to receive a user request for coaching information andmay present the requested coaching information. Also during the drive,the computer-executable instructions may further cause the computingdevice to predict a future drive event, such as an upcoming brake eventand/or upcoming turn event. In response to predicting a future driveevent, the computer-executable instructions may cause the computingdevice to present coaching information for the predicted future driveevent. After the drive, the coach's (e.g., parent's) smartphone maytransmit the coaching information to the driver's smartphone, so thedriver may review the coaching information. Aspects of the disclosurealso provide the computing device or apparatus including the computerreadable media storing such computer-executable instructions. Thecomputing device or apparatus may be a smartphone, tablet, laptop,vehicle's computing device (including a vehicle's in-dash displayscreen), etc.

Aspects of the disclosure further provide a method of collecting drivedata while a driver is driving a vehicle, detecting a drive event (e.g.,brake event, turn event, etc.) based on the drive data, and presentingcoaching information associated with the drive event in response todetecting the drive event. This method may further include retrievingdriver information from another computing device associated with thedriver (e.g., a driver's smartphone), determining the coachinginformation based on the driver information associated with the driver,and transmitting the coaching information to the driver's smartphone.The method may also include receiving a user request for a second pieceof coaching information, and presenting the second piece of coachinginformation. Further, the method may include providing a suggestedroute, predicting a future drive event using map information of thesuggested route, and presenting additional coaching informationassociated with the future drive event in response to predicting thefuture drive event. Still, in some examples, the method may also includerecording audio within the vehicle while the driver is driving, andtransmitting the recording to another computing device after the drive.

Of course, the methods and systems of the above-referenced embodimentsmay also include other additional elements, steps, computer-executableinstructions, or computer-readable data structures. In this regard,other embodiments are disclosed and claimed herein as well. The detailsof these and other embodiments of the present invention are set forth inthe accompanying drawings and the description below. Other features andadvantages of the invention will be apparent from the description,drawings, and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and is notlimited in the accompanying figures in which like reference numeralsindicate similar elements and in which:

FIG. 1 is a block diagram of an example computing device that may beused according to an illustrative embodiment of the present disclosure.

FIG. 2 illustrates an example network environment for implementingmethods according to the present disclosure.

FIG. 3 illustrates a flow diagram of an example process in accordancewith aspects of the present disclosure.

FIGS. 4A and 4B illustrate high-level diagrams of example interfacespresented by an application in accordance with aspects of the presentdisclosure.

FIG. 5 illustrates a flow diagram of an example process in accordancewith aspects of the present disclosure.

FIGS. 6A and 6B illustrate high-level diagrams of example interfacespresented by an application in accordance with aspects of the presentdisclosure.

DETAILED DESCRIPTION

In accordance with various aspects of the disclosure, methods,computer-readable media, software, and apparatuses are disclosed thatprovide a suite of pre-license applications that drivers, coaches, andvehicles may execute to provide an enhanced driver education experience.A pre-license coach application may execute on a passenger's userdevice, e.g., a smartphone, to collect drive data as a driver ispracticing driving, and to present coaching information that thepassenger may use to coach the driver during the drive. The pre-licensecoach application may give specific coaching information based on eventsoccurring during the drive. For example, the pre-license coachapplication may detect a brake event and/or turn event, and providecoaching information to the passenger so that the passenger may teach(or coach) the driver about braking and/or turning, respectively.

Meanwhile, a pre-license driver application may execute on a driver'suser device, e.g., a smartphone, to collect drive data as the driver isdriving. The pre-license driver application may then later present thedrive data to the driver so that he/she can learn about their drivingskills and improve their driving skills. The pre-license driverapplication may also present coaching information to educate the driveron how to improve. In some cases, the pre-license driver application maycause the driver's user device to output audible coaching informationthereby performing similar coaching functions that the pre-license coachapplication causes the passenger's user device to perform.

Additionally, a pre-license vehicle application may execute on avehicle's computing device to collect data about a drive as well. Thepre-license vehicle application may allow the vehicle's computing deviceto communicate with the driver's user device and/or passenger's userdevice. In particular, the pre-license vehicle application may transmitdata collected during a drive to the driver's user device and/orpassenger's user device. In some cases, the pre-license vehicleapplication may cause the vehicle's computing device to perform the samecoaching functions that the pre-license coach application causes thepassenger's user device to perform. Thus, the vehicle's computing devicemay present coaching information to the passenger that the passenger mayuse to teach the driver. Still, in some cases, the pre-license vehicleapplication may cause the vehicle's computing device to present thecoaching information directly to the driver.

Although a suite of pre-license applications (e.g., pre-license driverapplication, pre-license coach application, and pre-license vehicleapplication) are described above, these applications may be implementedas a single application. That is, a single application, herein referredto as the pre-license program, may be executed on various computingdevices which may perform particular modules of the pre-license program.As such, aspects of the disclosure may be implemented by variouscomputing devices (e.g., a driver's computing device, passenger'scomputing device, or vehicle's computing device) operating in tandem.

In the following description of the various embodiments of thedisclosure, reference is made to the accompanying drawings, which form apart hereof, and in which is shown by way of illustration, variousembodiments in which the disclosure may be practiced. It is to beunderstood that other embodiments may be utilized and structural andfunctional modifications may be made. Furthermore, the disclosures ofeach of the following patent applications are incorporated by referenceherein in their entirety: U.S. patent application Ser. No. 13/216,849,filed Aug. 24, 2011, entitled “In Vehicle Driver Feedback Device;” andthe concurrently-filed U.S. Patent Application entitled “InteractiveDriver Development” and identified as 13/826,429 in the law offices ofBanner & Witcoff, Ltd.

In one or more arrangements, teachings of the present disclosure may beimplemented with a computing device. FIG. 1 illustrates a block diagramof an example computing device 100 that may be used according to anillustrative embodiment of the present disclosure. The computing device100 may be similar to any available computing device, such as a personalcomputer (e.g., a desktop computer), server, laptop computer, notebook,tablet, smartphone, etc. The computing device 100 may have a pre-licensemanager 101 for performing methods and executing instructions of thepre-license program described herein. The pre-license manager 101 may beimplemented with a processor and memory and/or ASIC. Throughout thisdisclosure, the pre-license manager 101 may be used to reference acombination of the processor and memory storing instructions executed bythat processor and/or the instructions themselves. The processor of thepre-license manager 101 may operate in addition to or in conjunctionwith another processor 103 of the computing device 100. Both thepre-license manager 101 and the processor 103 may be capable ofcontrolling operations of the computing device 100 and its associatedcomponents, including RAM 105, ROM 107, an input/output (I/O) module109, a network interface 111, and memory 113.

The I/O module 109 may be configured to be connected to an input device115, such as a microphone, keypad, keyboard, touchscreen, and/or stylusthrough which a user of the computing device 100 may provide input data.The I/O module 109 may also be configured to be connected to a displaydevice 117, such as a monitor, television, touchscreen, etc., and mayinclude a graphics card. The display device 117 and input device 115 areshown as separate elements from the computing device 100, however, theymay be within the same structure. Using the input device 115, systemadministrators may update various aspects of the pre-license program,such as rules for detecting drive events and what coaching informationto provide in response to which drive events, described in furtherdetail below. On some computing devices 100, the input device 115 may beoperated by users to interact with the pre-license program, includingproviding user information, assessing a driver's performance, reviewinga driver's performance, etc., as described in further detail below.Meanwhile, the display device 117 may assist the system administratorsand users to confirm/appreciate their inputs.

The memory 113 may be any computer readable medium for storing computerexecutable instructions (e.g., software). The instructions stored withinmemory 113 may enable the computing device 100 to perform variousfunctions. For example, memory 113 may store software used by thecomputing device 100, such as an operating system 119 and applicationprograms 121, and may include an associated database 123.

The network interface 111 allows the computing device 100 to connect toand communicate with a network 130. The network 130 may be any type ofnetwork, including a local area network (LAN) and/or a wide area network(WAN), such as the Internet. Through the network 130, the computingdevice 100 may communicate with one or more computing devices 140, suchas laptops, notebooks, smartphones, personal computers, servers, etc.The computing devices 140 may also be configured in the same manner ascomputing device 100. In some embodiments the computing device 100 maybe connected to the computing devices 140 to form a “cloud” computingenvironment.

The network interface 111 may connect to the network 130 viacommunication lines, such as coaxial cable, fiber optic cable, etc. orwirelessly using a cellular backhaul or a wireless standard, such asIEEE 802.11, IEEE 802.15, IEEE 802.16 etc. In some embodiments, thenetwork interface may include a modem. Further, the network interface111 may use various protocols, including TCP/IP, Ethernet, File TransferProtocol (FTP), Hypertext Transfer Protocol (HTTP), etc., to communicatewith other computing devices 140.

The computing device 100 may be a mobile device (e.g., a smartphone),and thus, may also include various other components, such as a battery,speaker, and antennas (not shown).

The pre-license program disclosed herein may be implemented on acomputing device 100 used in various network environments. FIG. 2illustrates an example network environment 200 for implementing methodsaccording to the present disclosure. As shown in FIG. 2, the networkenvironment 200 may include a network 201 configured to connect one ormore administrative computing devices 100 a, one or more studentcomputing devices 100 b, one or more coach computing devices 100 c, andone or more vehicle computing devices 100 v. The network 201 may alsoprovide a path for connecting to application servers 203. The network201 may be any type of network, like the network 130 described above. Inparticular, the network 201 may include a cellular network and itscomponents, such as base stations, cell towers, etc. The networkenvironment 200 may include access points 205 to extend the network 201to reach mobile computing devices. The access points 205 may includecellular network components (e.g., cell towers, base stations, etc.),global positions system components (e.g., antennas, satellites, etc.),and other wireless access components (e.g., routers) for connecting thestudent computing devices 100 b, coach computing devices 100 c, and/orvehicle computing devices 100 v to the network 201. As such, through thenetwork 200, the student computing devices 100 b, coach computingdevices 100 c, and/or vehicle computing devices 100 v may communicatewith application servers 203 to obtain various information, such ascoaching information, driving statistics, maps, the time of day, weatherinformation, traffic information, position information, softwareupdates, etc.

In some embodiments, one or more of the application servers 203 may beconfigured to provide a service that receives drive data from users sothat users can review their drive data. For example, an applicationserver 203 may host a website that users can visit to see their drivedata and possibly the drive data of others. In some examples, the drivedata of a group of students (e.g., students in the same driving school)may be grouped together. An application server 203 may provide a webpagethat ranks students within their group (e.g., driving school) and/orthat ranks groups (e.g., driving schools) based on the performance oftheir students. Coaches may also access this service to see what skillsof their students should get more attention.

Referring to FIG. 2, the administrative computing device 100 a may beconfigured to generate, edit, manage, and deliver the suite ofpre-license applications (e.g., pre-license driver application,pre-license coach application, pre-license vehicle application, etc.) orpre-license program. The suite of pre-license applications orpre-license program may be downloaded, installed, and executed on one ormore student computing devices 100 b, coach computing devices 100 c,and/or vehicle computing devices 100 v. In some examples, theadministrative computing device 100 a may execute the pre-licenseprogram in tandem with a student computing device 100 b, coach computingdevice 100 c, and/or vehicle computing device 100 v. The server-sidecomputing device 100 a may, for example, render graphics and webpageswhich are then streamed to these other computing devices 100 b, 100 c,100 v which may be used to supply user inputs so that the user mayinteract with the pre-license program. As shown in FIG. 2, the studentcomputing device 100 b and coach computing device 100 c may be aportable user device, such as a smartphone, tablet, laptop, etc., that auser may take with them into a vehicle 207. Although FIG. 2 shows thevehicle 207 as being a car, the vehicle 207 may be a motorcycle, truck,bus, boat, plane, etc.

When the student computing device 100 b and coach computing device 100 care inside or near the vehicle 207, they may communicate with thevehicle computing device 100 v. In some examples, the vehicle computingdevice 100 v may include the vehicle's on-board diagnostic (OBD) system.The student computing device 100 b and/or coach computing device 100 cmay communicate with the vehicle computing device 100 v via a wiredconnection (e.g., USB, OBD II connector, etc.) or a wireless connection(e.g., Bluetooth).

FIG. 2 includes an exploded view of the inside of the vehicle 207 toillustrate example operating positions and lines of communication of thevarious computing devices. As shown, the driver, also referred to as thestudent since the driver may be learning to drive, may position his/herphone (an example of a student computing device 100 b) on a centerconsole or other flat surface within the vehicle 207. In some cases, thestudent computing device 100 b may be positioned out of reach and/orview of the driver during the drive as the driver may be expected tofocus on driving and not on using the student computing device 100 b.Meanwhile, a passenger (e.g., a parent, coach, etc.) of the vehicle 207,who intends to teach the student how to drive or how to improve atdriving, may hold or otherwise position his/her phone (an example of acoach computing device 100 c) so that he/she may view its screen, hearaudio from its microphone, and/or provide user inputs via its keypad,buttons, etc. Thus, when the coach computing device 100 c presentscoaching information, the passenger (or coach) may provide verbalfeedback to the student about his/her driving.

In some cases, instead of, or in addition to, receiving coachinginformation through their coach computing device 100 c, the passengermight receive the coaching information from the vehicle computing device100 v via a display of the vehicle 207. The vehicle computing device 100c may be installed behind the dashboard of a vehicle 207 (or elsewherein the vehicle). The driver or passenger may interface with the vehiclecomputing device 100 v by operating buttons on the dashboard, touching adisplay on the dashboard, or providing verbal commands.

FIG. 3 illustrates a flow diagram for an example process in accordancewith aspects of the present disclosure. More specifically, FIG. 3illustrates a plurality of steps a coach computing device 100 c mayperform to provide a passenger with coaching information that thepassenger may use to give advice to a student driver while driving. Oneor more of the steps of FIG. 3 may be performed as a result of executingthe pre-license program on the coach computing device 100 c.

As shown in FIG. 3, the process may begin with a step of configuring thecoach computing device 100 c in step 301. Configuring the coachcomputing device 100 c may include downloading and installing thepre-license program. Further, it may include entering information aboutthe driver and/or coach. For example, a user may enter the age of thedriver, the gender of the driver, the state the driver has a driver'spermit in (or the state that the driver intends to get his/her licensein), a date in which the user received his/her driver's permit, a datethe user expects to take a driver's test to receive a full license, etc.With regards to the coach, the user may enter the coach's age, coach'sgender, coach's driver license number, coach's insurance policy number,etc. At step 301, the user may also enter information about the vehicle,such as the make, model, and year of the vehicle.

Additionally, configuration may include registering the coach computingdevice 100 c with an application server 203 so that the coach computingdevice 100 c may receive data to carry out certain aspects of thecoaching process. For example, the coach computing device 100 c mayregister with an application server 203 to receive coaching informationor statistics related to other drivers and coaches so that driving andcoaching performance can be compared to others. Registration may includecreating a username and password to be associated with the coach and/oran account (e.g., insurance account) of the coach. Such registration maybe performed through a web portal, which may be accessed through thepre-license program. The registration process may also result increating a web page, hosted by the administrative computing device 100 aor application server 203, to which the coach computing device 100 c mayupload information, such as coaching information, and pictures.

At step 302, the coach computing device 100 c may synchronize with thestudent computing device 100 b and/or vehicle computing device 100 d.Synchronization may include establishing a connection (e.g., a Bluetoothconnection) for communicating information between the devices. In somecases, synchronization may also include establishing a reference time sothat data on one device may be correlated with data on another device.For example, synchronization may include establishing a reference timeso that the time at which a driver made a left turn can be correlatedwith the time at which a coach told the user to look out for othervehicles or with the time at which the vehicle's left turn signal wasactivated.

In step 303, the coach computing device 100 c may present pre-drivecoaching information. This may include displaying a checklist of thingsa student should do before beginning to drive. For example, thechecklist may include checking/adjusting mirrors, buckling a seatbelt,reminding passengers to buckle seatbelts, checking tires, checking oil,etc. The checklist may be interactive so that the coach may check offitems in the checklist as the driver performs them.

Additionally, the pre-drive coaching information may include advice forthe driver regarding an upcoming drive. For example, the pre-drivecoaching information may include advising the driver to focus on brakingearlier or going through turns at slower speeds. In some cases, thepre-drive coaching information may be customized for the particulardriver based on the driver's driving history. For example, if it isdetermined that the driver previously had difficulty braking smoothly,the pre-driving coaching information may inform the coach to remind thedriver that the driver should focus on braking smoothly. Or, if thedriver's past performances indicate that he/she has done well withturning at slow speeds, the pre-driving information may suggest advisingthe driver to work on turning at higher speeds in order to advance thedriver's skills.

Step 304 may include prompting the user to determine if the user wouldlike a suggested route. Some coaches may desire assistance pickingroutes suited for the driver or routes that give the driver variousdriving experiences. For example, a coach may want to take a route thathas less traffic so that the student can practice without the addedpressure of other drivers. Or, a coach might want the student topractice driving in certain conditions, e.g., driving on a highway, ifthe student has not had much experience in such conditions. Whenprompting the user at step 304, the pre-license program may give theuser a number of options for the user to select (e.g., less traffic,slower speeds, total drive time, etc.) that the pre-license program mayconsider when mapping a suggested route.

If the coach agrees to receive a suggested route (Yes at 304), thepre-license program may map one or more suggested routes at step 305. Inmapping suggested routes, the pre-license program may consider thedriver's history. For example, the pre-license program may determinethat the driver is ready to practice driving on the highway, and maysuggest a route that includes driving on a highway. Or, the pre-licenseprogram may determine that the driver needs more practice braking, andthus, may suggest a route that would require more stops. To aid insuggesting routes, the pre-license program may evaluate maps from thirdparty entities (e.g., Google Maps, Yahoo Maps, etc.). For example, ifthe pre-license program determines that the user should practice mergingonto a highway, the pre-license program may analyze map data todetermine where a nearby highway merger exists.

In step 306, the coach computing device 100 c may determine whether tostart collecting data for a drive. A user may indicate that a drive isstarting by pressing a button or otherwise making a user selection onthe coach computing device 100 c to indicate that the drive is starting.In some cases, step 306 may require the user to perform a calibrationprocess in which the user places the phone on a flat surface in astable, non-moving position. The coach computing device 100 c may thenestablish a reference orientation and speed so that it can begincollecting data using its GPS, 3-axis accelerometer, gyroscope, etc.

The pre-license program may begin to collect drive data, such as vehicletelematics data, at step 307. In particular, the pre-license program mayread data from the coach computing device's 100 c 3-axis accelerometer,gyroscope, and/or GPS at step 307 to collect some types of drive data,such as acceleration, deceleration, g-force, speed, etc. For example,the 3-axis accelerometer of the coach computing device 100 c may outputthe value of acceleration in an x-direction that the pre-license programmay equate to an acceleration of the vehicle in a forward direction.Thus, pre-license program may use capabilities of the coach computingdevice 100 c to get drive data. Notably, drive data is not limited totypes of movement data or vehicle telematics data, and may include anytype of data related to the drive, such as time of day information, dayor night information, weather conditions during the drive, roadconditions (e.g., side road or highway), traffic conditions (e.g.,light, medium, heavy, etc.), position information, etc. Some types ofdrive data, e.g., time of day, may be received from the coach computingdevice 100 c, while other types may be received from one or moreapplication servers 203 in communication with the coach computing device100 c.

Additionally, or alternatively, the pre-license program may collectdrive data from the student computing device 100 b. Specifically, datafrom a 3-axis accelerometer, gyroscope, and/or GPS of a studentcomputing device 100 b may be transmitted from the student computingdevice 100 c to the coach computing device 100 c. Therefore, the coachcomputing device 100 c might not use its own components to get the drivedata. For example, if the user (coach) of the coach computing device 100c is moving the coach computing device 100 c because, e.g., the coach isreading coaching information, talking on the phone, etc., the coachcomputing device 100 c may choose to use drive data from the studentcomputing device 100 b rather than its own drive data. However, in somecases, the pre-license program executing on the coach computing device100 c may consider drive data from both the coach computing device 100 cand the student computing device 100 b. For example, the pre-licenseprogram may compare the data generated by a 3-axis accelerometer of thesame device, that is, the coach computing device 100 c, with datagenerated by a 3-axis accelerometer of a student computing device 100 bto determine more accurate drive data. In some examples, the coachcomputing device 100 c may determine to average or otherwise merge theresults.

Further, in addition to, or instead of, receiving drive data from thestudent computing device 100 b, the coach computing device 100 c mayreceive drive data, including, e.g., vehicle telematics data, from thevehicle computing device 100 v. Specifically, the pre-license programmay cause the coach computing device 100 c to query the vehiclecomputing device 100 v of the vehicle 207 that it is inside to provideit with drive data. The vehicle computing device 100 v may then transmitdrive data that it has collected. Some vehicles may be equipped withsensors, 3-axis accelerometers, gyroscopes, GPS, etc. that provide themwith drive data that can be used by the pre-license program fordetecting events. The coach computing device 100 c may receive drivedata from the vehicle computing device 100 v via a wireless connection(e.g., Bluetooth) or a wired connection (e.g., OBD II connector).

As the coach computing device 100 c receives/collects drive data, thepre-license program may analyze the data to detect drive events at step308. A variety of drive events may be detected at step 308. The driveevents may be related to driving maneuvers (e.g., braking, turning,accelerating, decelerating, swerving, changing lanes, parking,tailgating, etc.). For example, vehicle telematics data may be analyzedto detect some types of drive events. Further, some drive events may berelated to driving characteristics (e.g., driving speed, a level ofalertness of driver, distractions during driving, etc.). For example,the pre-license program may detect that the driver is speeding based onspeed limit information. In another example, cameras monitoring thedriver's eyes or head position may provide information that thepre-license program may use to detect that the driver is not focusing onthe road. Yet another example may include analyzing setting changes(e.g., changing a radio station or volume, answering a phone, sending atext message, etc.), to detect a drive event indicating that the drivermay have been distracted during the drive. Additionally, some driveevents may be related to driving conditions (e.g., time of day, weatherconditions, road conditions, traffic conditions, etc.). For example, thepre-license program may use weather information obtained during thedrive to determine that it is raining during the drive.

In particular, in step 308, the pre-license program may detect whether abrake event occurred based on data collected at step 307. Specifically,the pre-license program may use one or more algorithms to analyze thedrive data to detect a brake event. For example, braking may beassociated with deceleration data, and therefore, by analyzing suchdata, the pre-license program may determine whether a brake event hasoccurred. More specifically, a braking event may be detected ifdeceleration data indicates a threshold change in speed was exceeded(e.g., the vehicle speed decreased by at least 20 mph) and a minimumspeed threshold was reached (e.g., the vehicle slowed down to 1 mph).Other algorithms may also be used to detect a brake event.

The pre-license program may also detect whether a turn event occurred atstep 308. Specifically, the pre-license program may use one or morealgorithms to analyze the data to detect a turn event. For example,turning may be associated with g-force data, and therefore, by analyzingsuch data, the pre-license program may determine whether a turn eventhas occurred. More specifically, a turning event may be detected if theg-force reaches a particular level (e.g., 1 g) and maintains that levelfor a particular period of time (e.g., 2 seconds). Other algorithms mayalso be used to detect a turn event.

In response to detecting an event, such as a brake event or turn event,the pre-license program may cause the coach computing device 100 c topresent coaching information at step 309. Presenting the coachinginformation may include displaying the coaching information on a screen(or display) of the coach computing device 100 c and/or outputting anaudible message via the coach computing device 100 c. The coachinginformation presented may be related to the detected event. For example,if a brake event was detected, the coaching information may includeadvice to the coach to tell the driver how he/she might improvebreaking. Accordingly, coaching information may be presented to thecoach in real-time as the user is driving, so that the coach mayinstruct the student in real-time.

In preparing the coaching information, the pre-license program maycompare the drive data of the drive event to standards for the driveevent. For example, the pre-license program may compare drive data for aturn event with standards developed for what the drive data for a turnevent should be. Based on how similar the drive data for the driver'sdrive event compares against the standard data for that drive event, thepre-license program may recommend praising the driver. For example, ifthe driver made a turn that the pre-license program determined waswithin some threshold of ideal drive data for a turn, the pre-licenseprogram may prepare coaching information that suggests praising thedriver for his/her turn.

The coaching information presented at step 309 may also depend on thedriver's skill level/experience. That is, for more advanced drivers, thecoaching information may include more details. Accordingly, as thedriving skills of a student progress, the coaching information maybecome more advanced and may focus on the finer points of driving. Thepre-license program may assess the driver's skill/experience based onpast drive data. In particular, the pre-license program may consider thenumber of minutes the student has driven, the number of drive events thestudent performed, and/or how well the student performed drive events.Notably, the pre-license program may determine that the student is moreadept in some areas of driving than others. For example, the pre-licenseprogram may determine that a student is more advanced/experienced atbrake events than turn events, and therefore, the coaching informationit suggests for that student may be more detailed for brake events thanturn events.

The coaching information may also be based on driving characteristicsand driving conditions. For example, if it is detected that the driveris not focusing on the road, the coaching information may provide advicethat the driver should look at the road. The coaching information mayalso include statistics, such as a percentage of accidents caused bydrivers not looking at the road, so that the coach may inform the driverof the potential consequences of the driver's behavior. In anotherexample, if it is detected that the driver is driving in the rain, thecoaching information may include providing advice for how to drive inthe rain, such as how to avoid hydroplaning or what to do in the eventof hydroplaning.

In addition to presenting the coaching information to the coach, thepre-license program may cause the coach computing device 100 c toprovide audio feedback that the driver can hear. This audio feedback maybe an audible message corresponding to the coaching information, inwhich case the coach might not have to provide the instructions.Alternatively, the audio feedback may simply provide various sounds(e.g., beeps) that the driver may recognize as being a positive ornegative response to their driving performance.

FIG. 4A illustrates an example of coaching information that thepre-license program may present on the coach computing device 100 c. Asshown, the coaching information may include a driving tip for the coachto explain to the student. In the example of FIG. 4A, the driving tipmay include the message “brake before, not during, a turn.” This tip maybe generated based on the drive data collected for a recently detectedturn event. Here, based on the drive data, the pre-license program mayhave determined that the driver did not brake enough before the turn,and instead, used the brake too much in the turn. Using the results ofthis determination, the pre-license program may then generate thecoaching information and present it to the coach as shown.

FIG. 4B illustrates another example of coaching information that thepre-license program may present on the coach computing device 100 c. Asshown, the coaching information may include a coaching suggestion forthe coach. In the example of FIG. 4B, the driving suggestion may includethe message “consider trying the freeway soon.” This driving suggestionmay therefore inform the coach that the student is ready to, or shouldattempt to, drive on a freeway. Such a driving suggestion may begenerated based on the collected drive data. For example, if thecollected drive data indicates that the user is braking and/or turningwell at slow speeds, the driving suggestion may be to try the freeway.The pre-license program may also consider how much time the driver hasspent driving in determining what suggestions to make. Moreover, thepre-license program may review past driving experiences when generatingsuggestions. For example, the pre-license program may check a drivinghistory and determine that the user has not yet driven on a freeway, andthen prepare the driving suggestion that the student should considerdriving on the freeway.

Returning to FIG. 3, step 310 may include detecting a potential futuredrive event, that is, a drive event that has not yet occurred. Thepre-license program may predict a future drive event using mapinformation and position information (e.g., GPS data). In cases wherethe pre-license program has suggested a route or knows of a route, thepre-license program may determine that certain drive events are comingup. For example, the pre-license program may analyze a route and thelocation of the vehicle along that route to determine that a turn eventis likely to occur soon. Or, the pre-license program may analyze theroute to identify a stop sign that the vehicle is approaching, andtherefore, may determine that a brake event is likely to occur soon.

When a future drive event is detected, the pre-license program mayprovide coaching information related to the future event to the coachcomputing device 100 c in advance of the future drive event. That is, atstep 311, the pre-license program may present coaching information fordrive events that have not yet occurred, but are expected to occur. Thecoach may use this coaching information to provide instruction to thedriver for handling the future drive event. The pre-license program mayalso inform the coach of a timing for providing the driver withinstructions. For example, the pre-license program may determine thatthe vehicle is located 100 feet from a stop sign, and therefore, mayrecommend that the coach provide instructions to tell the driver tostart slowing down at this point. The pre-license program may alsofactor in the speed of the vehicle when determining the ideal time thatthe instruction should be given.

In some embodiments, when, or after, the coach computing device 100 cpresents coaching information, the pre-license program may also promptthe coach for user input related to the coaching information. Forexample, the pre-license program may prompt the coach to provide inputas to whether or not the coaching information was provided to thestudent or otherwise accepted. In some cases, coaches might decide notto provide the coaching information to the student, and instead remainsilent or give their own instructions. In such cases, the coach mayprovide user inputs indicating that it rejected or did not provide thecoaching information to the student. On the other hand, the coach maychoose to provide the coaching information to the student and mayprovide an input indicating that the coaching information was given.

Moreover, when, or after, presenting the coaching information and/orprompting the coach for user input regarding whether the coachinginformation was given, the pre-license program may also prompt the coachfor input as to whether or not the student followed the coach's advice(e.g., performed the action recommended by the coaching information).The coach may provide an input indicating whether they believe thedriver followed the advice or did not follow the advice (e.g., ignoredthe advice or failed to follow the advice). Accordingly, the pre-licenseprogram may allow the coach to subjectively score, rate, or otherwisegrade the driver's performance and/or ability to follow the coachingadvice.

In step 312, the pre-license program monitors user inputs to check foruser requests. At times, a coach may want to request particular coachinginformation whether or not the user has performed a related drive eventor will perform a related drive event in the near future. That is, thecoach may want to provide instructions for a particular drive event eventhough the pre-license program has not detected that event. Accordingly,the coach may request specific coaching information by navigatingthrough predefined categories of coaching information and/or performinga keyword search. Based on the user's request, the pre-license programmay retrieve the appropriate coaching information at step 313.

Step 314 may include determining whether the drive has ended. In somecases, the pre-license program may automatically determine that thedrive has ended if the car has not moved for a predetermined period oftime (e.g., 10 minutes). On the other hand, the pre-license program mayrely on the user to inform it that the drive has ended. Notably, as longas the drive continues, the pre-license program may continue to performsteps 307-313. Moreover, it should be understood that these steps do nothave to be performed in the order shown. For example, the pre-licenseprogram may detect a future drive event before it detects a drive eventthat has already occurred. Further, the pre-license program may presentcoaching information for multiple past drive events before presentingcoaching information for a future drive event. Also, user requests forparticular coaching information may be received and handled at any timeduring the drive. In short, the order that steps 307-313 are performedwill depend on the events of the particular drive and the user inputsduring that drive.

After the drive is over, at step 315, the coach computing device 100 cmay exchange drive data with other computing devices, such as thestudent computing device 100 b and vehicle computing device 100 v. Forexample, the coach computing device 100 c may share the coachinginformation it presented during the drive with the student computingdevice 100 b, so that the student may view the coaching information onhis/her own device. Additionally, or alternatively, the coach computingdevice 100 c may share a recording of the coach's instructions to thedriver that the coach computing device 100 c recorded using itsmicrophone. Further, the coach computing device 100 c may provide areport of the inputs that the coach made during the drive. For example,the coach computing device 100 c may provide a report showing whichcoaching information the coach accepted or provided and which coachinginformation the coach rejected or did not provide. Such a report mayalso indicate which coaching advice the coach thought the studentfollowed and which coaching advice the coach thought the student did notfollow. As such, a student computing device 100 b receiving such reportsmay give the student the opportunity to review the coach's decisions andthoughts about the student's driving performance.

In step 315, the coach computing device 100 c may also uploadinformation to an administrative computing device 100 a or applicationserver 203 via the network 201. Such information may include a number ofminutes spent coaching/training the student driver. This information maybe compiled at the administrative computing device 100 a or applicationserver 203 so that statistics reflecting how much time coaches arespending on training student drivers can be generated. Other types ofinformation may be uploaded as well. The coach computing device 100 cmay include a camera, and therefore, may be used to take photographs ofthe student while he/she is driving. The coach computing device 100 ccould also be used to take photographs of various driving experiences,such as the student's first flat tire, first time driving to the beach,etc. The pre-license program may facilitate posting or sharing thesephotographs on a webpage hosted by the administrative computing device100 a or application server 203.

Step 316 illustrates that the pre-license program may provide the coachwith coaching history data. The pre-license program may store drive dataand a log of coaching information that it presented to the coach aftereach drive. As the pre-license program is used for a number of drives,the pre-license program may compile the data for each drive to preparean overview of the student's and/or coach's performance. For example,the pre-license program may prepare a report showing the coachinginformation that was previously provided on a drive-by-drive basis. Thecoach history data may also show how many minutes the coach has spentteaching the student. Further, the coach history data may providestatistics acquired from other coaches to show the coach how much timeother coaches are spending teaching their students. From suchstatistical information, coaches may assess themselves and determinewhether they should be spending more time training their student.

Although FIG. 3 depicts step 316 as the last step, it should beunderstood that the coaching history data may be viewed at any time andthat other steps may be performed after it. In general, FIG. 3illustrates steps in an example order, but the steps may be implementedin various orders. Indeed, the various features and steps may becombined, divided, omitted, and/or augmented in any desired manner,depending on the specific process desired. For example, the pre-licenseprogram may present route suggestions as described with respect to steps304 and 305 during the drive as well. Also, the user could requestcoaching information, as described with respect to step 312, before orafter drives. The processes of the pre-license program should not belimited to the example embodiments described.

FIG. 5 illustrates a flow diagram for an example process in accordancewith aspects of the present disclosure. More specifically, FIG. 5illustrates a plurality of steps a student computing device 100 b mayperform to provide a student with feedback as they learn to drive. Oneor more of the steps of FIG. 5 may be performed as a result of executingthe pre-license program on the student computing device 100 b.

As shown in FIG. 5, the process may begin with a step of configuring thestudent computing device 100 b in step 501. The configuration in step501 may be performed in a similar manner to the configuration in step301 of FIG. 3. That is, the configuration may include calibrating thestudent computing device 100 b and registering the student with theadministrative computing device 100 a or an application server 203. Inthe registration process, students may set up a profile for themselves.They may provide their name, age, driver's permit number, state they aretrying to receive a driver's license in, etc. Students may also set upprofiles for coaches that they anticipate having (or have had) teachthem to drive. For example, a teenager may set up a profile for each ofhis/her parents so that the teenager can track which parent is givingwhich instructions, which parent is spending more time training theteenager, etc.

Steps 502-506 may be similarly performed on the student computing device100 b in a similar manner that steps 302-306 are performed on the coachcomputing device 100 c. However, on the student computing device 100 b,when the drive is started (Yes at step 506), the student computingdevice 100 b may turn off its display. The pre-license program may causethe student computing device 100 b to turn off its display at step 507so that the student is not distracted by the display. While the user isdriving, the pre-license program might only display a screen on thestudent computing device 100 b that allows the user to stop the drive.That is, the pre-license program executing on the student computingdevice 100 b may determine that coaching information should not bedisplayed while the user is driving.

In some embodiments, the pre-license program may cause certain functionsof the student computing device 100 b to be inoperable while the studentis driving. For example, the pre-license program may preventincoming/outgoing phone calls and text messages (e.g., SMS messages). Asa result, the pre-license program may help reduce the likelihood thatthe student becomes distracted by the student computing device 100 bwhile driving.

At step 508, the pre-license program may cause the student computingdevice 100 b to collect drive data, such as vehicle telematics data.Drive data may be collected from the student computing device 100 b in asimilar manner that drive data is collected from the coach computingdevice 100 c as described above. That is, the pre-license program maycollect drive data from a 3-axis accelerometer, gyroscope, GPS, etc. ofthe student computing device 100 b. Additionally, or alternatively, thepre-license program executing on the student computing device 100 b mayreceive the drive data from the vehicle computing device 100 v and/orthe coach computing device 100 c. Also, at step 509, drive events may bedetected based on the collected drive data. Notably, the pre-licenseprogram may collect drive data and detect drive events without notifyingthe student during the drive so as not to distract the student.

Although FIG. 5 does not show steps for presenting coaching information,in some embodiments, the student computing device 100 b may generate andpresent coaching information. In particular, the student computingdevice 100 b may present audible messages providing the coachinginformation so that the student does not have to rely on the coach forsuch coaching information.

Step 510 illustrates that the student computing device 100 b maytransmit drive data while the student is driving. As described above,the drive data may be collected on the student computing device 100 band transmitted to the coach computing device 100 c, which may use theinformation to present coaching information.

At step 511, the pre-license program may determine whether the studenthas finished a drive. This may include determining that the vehicle hasnot moved for some predetermined period of time (e.g., 2 minutes) orreceiving an indication from the user that the drive has ended (e.g.,the user may press a key on the student computing device 100 bindicating the end of the drive). After the drive, in step 512, thestudent computing device 100 b may exchange data with other devices,such as the administrative computing device 100 a, the coach computingdevice 100 c, and/or vehicle computing device 100 v. For example, thestudent computing device 100 b may send/receive an audio recording ofthe sound in the car during the drive. This recording, therefore, mayinclude the dialogue between the coach and student, including what tipsthe coach gave the student. The student may be able to subsequentlylisten to the audio recording to see what his/her coach said and tocompare it against the coaching information which indicates what thecoach should have said.

In step 513, the pre-license program may store the collected drive dataand information received from other devices on the student computingdevice 100 b. In some cases, this data/information may be transmitted toan administrative computing device 100 a and/or application server 203and stored in association with the student or student computing device100 b.

In step 514, the pre-license program may generate and present reports tothe student. These reports may provide feedback on how the userperformed during the most recent drive and how the user is progressing.This feedback may be presented with graphs, charts, and otherillustrations. The feedback may also be divided into categories toassess various driving skills, such as braking, turning, etc. Thereports may also include tips for improving the student's drivingskills. Further, the reports may show which goals the user hasaccomplished and which goals remain. The pre-license application mayinclude a checklist of skills that are tested during a driving test, sothe student can keep track of their preparation for the driving test.For example, if parallel parking is required on a driving test, thepre-license program may keep a record of the number of times the studenthas practiced parallel parking and a score associated with each attempt.The score may be generated by the coach using the coach computing device100 c and transmitted to the student computing device 100 b. Thepre-license program may assist the coach in scoring so that the coachgives consistent scores and progress can be tracked. In some cases, thepre-license program may generate the score itself based on enteredinformation, such as the distance between the car and curb afterparallel parking. The reports may also keep a log of mandatorypre-license driving time. For states that require a certain amount ofdriving time, the pre-license program can keep track of the amount oftime the student has driven, so that it can be determined whether thestudent has met the requirements, or on track to meet the requirements,for the state he/she hopes to obtain a license in.

FIG. 6A illustrates examples of progress reports that the pre-licenseprogram may present on the student computing device 100 b at step 514.As shown, the progress reports may include bar graphs to reflect thestudent's driving experience/skill in a number of categories. In theexamples of FIG. 6A, the categories in which the student is assessedinclude day driving, night driving, highway driving, scanning ahead,smoothness, total time (e.g., hours) of driving. The values for thecategories may be calculated by the pre-license program based on variousalgorithms using various thresholds.

Some values may be directly proportional to an amount of time drivingunder certain conditions. For example, the value of the night drivingcategory may be a reflection of the number of minutes a user has drivenat night. Information regarding whether a student is driving at night orday may be included within the drive data collected at step 508.Standards may be established setting forth the ideal/recommended amountof time a student should spend driving at night. Then, the amount oftime the student has spent driving at night may be compared to thesestandards to receive a score or percentage as shown.

On the other hand, some values may be determined based on subjectiveand/or objective data collected at step 508. For example, the scanningahead score of FIG. 6A may be based on subjective data entered by acoach via a coach computing device 100 c. The pre-license programrunning on the student computing device 100 b may receive the subjectivescore from the coach and incorporate it into its reports. Meanwhile, thesmoothness score may be based on objective drive data collected in step508. The pre-license program executing on the student computing device100 b may analyze acceleration and deceleration data collected throughthe student computing device 100 b, coach computing device 100 c, and/orvehicle computing device 100 v. Specifically, the pre-license programmay compare such acceleration and deceleration data with predefinedthresholds to determine how smoothly the student is driving. Generally,constant or gradually increasing acceleration and constant or graduallydecreasing deceleration may indicate smooth driving.

FIG. 6A also illustrates that the pre-license program may prescribedifferent levels (e.g., level 1, level 12, etc.) to students as theirskills and experience progress. As a student demonstrates better drivingskills and/or acquires more driving experience (e.g., in terms ofdriving time), the pre-license program may determine that the user hasreached different levels. For example, the pre-license program maydetermine that the student has reached level 2 when the student exceedsa first minimum threshold in a set of categories and reached level 3when the student exceeds a second minimum threshold, higher than thefirst minimum threshold, in the set of categories. By prescribing levelsto the students, the pre-license program may help the user appreciatetheir improvements and incentivize or encourage the student to continueto work on their driving skills.

FIG. 6B illustrates examples of additional feedback that the pre-licenseprogram may present on the student computing device 100 b at step 514.As shown, the pre-license program may recognize certain accomplishmentsachieved by the student and may reward the student with badges 601.Similar to prescribing levels, the pre-license program may prescribecertain badges 601 to highlight certain student achievements as they thestudent advances towards driving proficiency. For example, the studentmay receive a “Night Owl” badge if they drive a total of 3 hours in thedark. In another example, the student may receive a “Globe Trotter”badge if they drive for a certain number of miles or for a certainperiod of time in a single drive.

Aspects of the invention have been described in terms of illustrativeembodiments thereof. Numerous other embodiments, modifications, andvariations within the scope and spirit of the appended claims will occurto persons of ordinary skill in the art from a review of thisdisclosure. For example, one of ordinary skill in the art willappreciate that the steps illustrated in the illustrative figures may beperformed in other than the recited order, and that one or more stepsillustrated may be optional in accordance with aspects of the invention.

What is claimed is:
 1. An apparatus, comprising: an accelerometer,gyroscope, or global positioning system receiver configured to detectdrive data while a vehicle is being driven; a display; at least oneprocessor; and memory storing computer-executable instructions that,when executed by the at least one processor, cause the apparatus to:activate the accelerometer, gyroscope, or global positioning systemreceiver to detect drive data; receive a user request for first coachinginformation while the accelerometer, gyroscope, or global positioningsystem receiver is activated; upon receiving the user request, present,on the display, the first coaching information while the accelerometer,gyroscope, or global positioning system receiver is activated, whereinthe first coaching information includes a suggested route based ondriving conditions and driver information associated with a driver ofthe vehicle; detect a drive event based on received drive data; inresponse to detecting the drive event, present, on the display, secondcoaching information associated with the drive event; present, on thedisplay, a prompt requesting user input related to the second coachinginformation, the user input including whether the driver followed thesecond coaching information and a performance rating of the driver; andpresent, on the display, a drive summary including the first coachinginformation and the second coaching information.
 2. The apparatus ofclaim 1, wherein said computer-executable instructions further cause theapparatus to: detect, based on received drive data, that the vehicle isno longer being driven; and upon detecting that the vehicle is no longerbeing driven, deactivate the accelerometer, gyroscope, or globalpositioning system receiver.
 3. The apparatus of claim 1, wherein thesecond coaching information is based on driver information associatedwith the driver.
 4. The apparatus of claim 1, wherein saidcomputer-executable instructions further cause the apparatus to:retrieve driver information from another computing device associatedwith the driver; and transmit the first coaching information and secondcoaching information to the other computing device associated with thedriver.
 5. The apparatus of claim 1, wherein the drive data includes atleast one of acceleration data and location data.
 6. The apparatus ofclaim 1, wherein the drive event comprises at least one of a brake eventand a turn event.
 7. The apparatus of claim 1, wherein saidcomputer-executable instructions further cause the apparatus to: predicta future drive event; and present third coaching information associatedwith the future drive event in response to predicting the future driveevent.
 8. A method, comprising: activating a sensor system associatedwith a vehicle to detect drive data while a driver is driving thevehicle, the drive data including at least one of acceleration data andlocation data; presenting, on a display associated with the vehicle,first coaching information while the sensor system is activated, whereinthe first coaching information includes a suggested route based on askill level of the driver and driving conditions; receiving, by at leastone processor, drive data while sensor system is activated; detecting adrive event based on received drive data; in response to detecting thedrive event, presenting, on the display associated with the vehicle,second coaching information associated with the drive event; presenting,on the display associated with the vehicle, a prompt requesting userinput related to the first coaching information, the user inputincluding whether the driver followed the first coaching information anda performance rating of the driver; and providing, on the display, adrive summary including the first coaching information and the secondcoaching information.
 9. The method of claim 8, wherein the sensorsystem includes at least one of an accelerometer, gyroscope and globalpositioning system receiver.
 10. The method of claim 8, furthercomprising: receiving a user request for first coaching informationwhile the sensor system is activated, wherein the first coachinginformation is presented upon receiving the user request.
 11. The methodof claim 8, further comprising: detecting, based on the drive data, thatthe driver is no longer driving the vehicle; and upon detecting that thedriver is no longer driving the vehicle, deactivating the sensor system.12. The method of claim 8, further comprising: retrieving driverinformation from another computing device associated with the driver;and determining the second coaching information based on the driverinformation.
 13. The method of claim 8, wherein the drive eventcomprises at least one of a brake event and a turn event.
 14. The methodof claim 8, further comprising: predicting a future drive event usingmap information of the suggested route; and in response to predictingthe future drive event, presenting, on the display, third coachinginformation associated with the future drive event.
 15. A non-transitorycomputer readable media storing computer-executable instructions that,when executed by at least one processor, cause a computing device to:activate a sensor system to detect drive data while a driver is drivinga vehicle; present, on a display of the computer device, first coachinginformation while the sensor system is activated, wherein the firstcoaching information includes a suggested driving route based on a skilllevel of the driver and driving conditions; detect a drive event basedon received drive data while the driver is driving the vehicle; inresponse to detecting the drive event, present, on the display of thecomputing device, second coaching information associated with the driveevent; and present, on the display, a prompt requesting user inputrelated to the second coaching information, the user input includingwhether the driver followed the second coaching information, and aperformance rating of the driver.
 16. The non-transitory computerreadable media of claim 15, wherein the sensor system includes at leastone of an accelerometer, a gyroscope and a global positioning systemreceiver, and wherein the drive data includes at least one ofacceleration data and location data.
 17. The non-transitory computerreadable media of claim 15, wherein said computer-executableinstructions further cause the computing device to: detect, based on thedrive data, that the driver is no longer driving the vehicle; and upondetecting that the driver is no longer driving the vehicle, deactivatethe sensor system.
 18. The non-transitory computer readable media ofclaim 17, wherein said computer-executable instructions further causethe computing device to: upon deactivating the sensor system, provide,on the display, a drive summary including the first coaching informationand the second coaching information.
 19. The non-transitory computerreadable media of claim 15, wherein said computer-executableinstructions further cause the computing device to: receive a userrequest for coaching information while the sensor system is activated,wherein the first coaching information is presented upon receiving theuser request.
 20. The non-transitory computer readable media of claim19, wherein said computer-executable instructions further cause thecomputing device to: retrieve driver information from another computingdevice associated with the driver; and determine the second coachinginformation based on the driver information associated with the driver.